Carrier agnostic relay for delivering information to autonomous vehicles

ABSTRACT

A device receives a first message indicating that content was transmitted to a telemetry device, generates and sends a second message to a remote device. The device receives a third message from the remote device including first information identifying the remote device and second information identifying a neighbor device of the remote device, and generates and sends a fourth message to the remote device, causing the remote device to download the content via a link and send the fourth message to the neighbor device, which causes the neighbor device to download the content via the link. The device receives a fifth message from the remote device including third information indicating whether the remote device and the neighbor device downloaded the content via the link, and generates and sends, to the base station, a sixth message including the first information, the second information, and the third information.

BACKGROUND

Vehicle to network (V2N) services can provide a wide area networkinterface (e.g., a long term evolution (LTE) interface) to connectend-user devices and vehicles to mobile network base stations and mobilecore networks. Vehicle to vehicle (V2V) services can provide a directcommunications interface (e.g., an LTE PC5 interface) that can connectvehicles to vehicles.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1F are diagrams of example implementations described herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, can be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a diagram of example components of one or more devices of FIG.2.

FIGS. 5A-5B are diagrams of a call flow of example operations capable ofbeing performed by one or more devices of FIG. 2 and/or one or morecomponents of one or more devices of FIG. 2.

FIG. 6 is a flow chart of an example process for a carrier agnosticrelay for delivering information to autonomous vehicles.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

Autonomous vehicles can rely on both internal data sources and externaldata sources during operation. With respect to internal data sources,autonomous vehicles can include a large number of embedded computers,hardware controllers, global positioning system (GPS) receivers, andconnectivity components that each can generate and receive significantamounts of data.

In order to operate effectively, efficiently, and safely, autonomousvehicles might also receive, process, and/or interpret informationassociated with external data sources (e.g., content). For example, theinformation can include status data of nearby infrastructure, trafficdata, data related to safety hazards, or the like. In order to utilizesuch information, autonomous vehicles might need to access a potentiallylarge volume of information, and/or might need to access and/or processthe information substantially instantaneously. In some cases, a providerof a cellular connection service can send the information via a cellularconnection to autonomous vehicles that subscribe to the cellularconnection service. However, in some cases, some of the autonomousvehicles may not subscribe to the cellular connection service providedby the provider, and therefore cannot receive the information from theprovider via the cellular connection service. This can create a gap inensuring that autonomous vehicles travelling on a road have theinformation that the autonomous vehicles need to operate effectively,efficiently, and safely, which can create dangerous driving conditionsfor all vehicles travelling on the road, regardless of whether thevehicles are operated autonomously or not. This can also createhazardous conditions for people, animals, and property that travel onthe road (e.g., pedestrians that walk along or across the road on whichthe autonomous vehicles travel) and/or are located alongside the road(e.g., a house located at a corner of an intersection of the road onwhich the autonomous vehicles travel).

Some implementations described herein provide a system of a firstautonomous vehicle for receiving information from a base station of aprovider (e.g., via a long term evolution (LTE) multicast connection)and directly communicating with a system of a second autonomous vehicleto ensure that the system of the second autonomous vehicle and a systemof a third autonomous vehicle receive the information. In someimplementations, the system of the first autonomous vehicle can createand transmit messages to the system of the second autonomous vehicle viaa direct communications interface (e.g., an LTE PC5 interface). In someimplementations, the system of the first autonomous vehicle can receivemessages from the system of the second autonomous vehicle via the directcommunications interface. In some implementations, the system of thesecond autonomous vehicle can send messages to and receive message fromthe system of the third autonomous vehicle via the direct communicationsinterface. In some implementations, the system of the first autonomousvehicle can determine identifying information of the second autonomousvehicle and the third autonomous vehicle by generating a query message,sending the query message to the system of the second autonomousvehicle, and receiving a query response message from the system of thesecond autonomous vehicle. In some implementations, the system of thefirst autonomous vehicle can generate and send a relay message to thesystem of the second autonomous vehicle that includes a link to theinformation, which causes the system of the second autonomous vehicle todownload the information via the link and forward the relay message tothe system of the third autonomous vehicle, which causes the system ofthe third autonomous vehicle to download the information via the link.In some implementations, the system of the second autonomous vehicle cansend a status message to the system of the first autonomous vehicle thatindicates whether the system of the second autonomous vehicle and thesystem of the third autonomous were able to download the information. Insome implementations, the system of the first autonomous vehicle cansend a report to the base station of the provider that indicates whetherthe information was delivered to the system of the second autonomousvehicle and the system of the third autonomous vehicle.

In this way, some implementations described herein permit informationtransmitted by the base station of the provider to be delivered to thesystem of the first autonomous vehicle, the system of the secondautonomous vehicle, and the system of the third autonomous vehicle. Inthis way, some implementations described herein allow the system of thefirst autonomous vehicle to facilitate delivery of the information tothe system of the second autonomous vehicle and the system of the thirdautonomous vehicle, even if the second autonomous vehicle and the thirdautonomous vehicle are outside a service area of the base station and/orthe second autonomous vehicle and the third autonomous vehicle do notsubscribe to the cellular connection service associated with the basestation of the provider. In this way, some implementations allow forefficient network usage and efficient use of network bandwidth byefficient distribution of the information to the system of the firstautonomous vehicle, the system of the second autonomous vehicle, and thesystem of the third autonomous vehicle. In this way, someimplementations require reduced communication and/or signaling relativeto communications between the base station and the system of the firstautonomous vehicle, the system of the second autonomous vehicle, and thesystem of the third autonomous vehicle. In this way, someimplementations described herein conserve processor and/or memoryresources of devices associated with the autonomous vehicles and basestation, and/or conserve network resources. In this way, someimplementations increase the amount of information that is available tothe autonomous vehicles, which can improve effectiveness, efficiency,and safety of how the autonomous vehicles operate.

FIGS. 1A-1F are diagrams of example implementations 100 describedherein. As shown in FIG. 1A, example implementation 100 can include abase station and a set of vehicles (e.g., vehicle 1, vehicle 2, andvehicle 3). The set of vehicles can include autonomous vehicles,semi-autonomous vehicles (e.g., vehicles that are autonomous in aparticular geographic area, at a particular speed, for a particularpurpose, and/or the like), and/or vehicles that utilize an autonomousapplication (e.g., autonomous driving systems, advanced driverassistance systems, autonomous braking systems, advanced brakingassistance systems, and/or the like). As shown, the set of vehicles cantravel on a road (e.g., a dirt road, a city street, a highway, and/orthe like). In some implementations, each vehicle of the set of vehiclescan have a system to facilitate communicating with the base station, viaa cellular connection, and/or the system of each of the other vehiclesof the set of vehicles, via direct communications, while traveling onthe road. In some implementations, the system can comprise one or morethan one device.

As further shown in FIG. 1A, the base station can have a service area.In some implementations, a service area can refer to a particulargeographic area, an area associated with a geofence, an area in which abase station can provide a cellular connection to communicate with thesystem of a vehicle, a set of cells covered by a set of base stations,and/or the like. For example, as shown, the base station can have aservice area (e.g., service area 1) in which the base station canprovide a cellular connection to communicate with the system of vehicle1 via multicast transmissions. Vehicle 2 and vehicle 3 can be outsidethe service area and therefore the systems of vehicle 2 and vehicle 3,respectively, are unable to communicate with the base station via thecellular connection. In some implementations, vehicle 2 and/or vehicle 3can be within the service area of the base station, but the systems ofvehicle 2 and/or vehicle 3, respectively, cannot communicate with thebase station via the cellular connection because the systems of vehicle2 and/or vehicle 3 do not subscribe to a cellular connection servicethat provides the cellular connection associated with the base station.

As shown in FIG. 1B, a vehicle can have a relay area. In someimplementations, a relay area can refer to a particular geographic areaaround the vehicle (e.g., a radius around the vehicle), an areaassociated with a geofence around the vehicle, an area in which thesystem of the vehicle can communicate with the system of another vehiclevia direct communications, and/or the like. For example, as shown,vehicle 1 can have a relay area (e.g., relay area 1) in which the systemof vehicle 1 can communicate with the system of vehicle 2 via directcommunications (e.g., via a long term evolution (LTE) PC5 interface, anInstitute of Electrical and Electronics Engineers (IEEE) 802.11pinterface, and/or the like). As shown, vehicle 2 can have a relay area(e.g., relay area 2) in which the system of vehicle 2 can communicatewith the system of vehicle 1 and/or the system of vehicle 3 via directcommunications. In some implementations, vehicle 3 can have a relay areain which the system of vehicle 3 can communicate with the system ofvehicle 2 via direct communications. In some implementations, a vehiclecan have a relay area in which the system of the vehicle can communicatewith the systems of multiple vehicles via direct communications.

As shown in FIG. 1C, the base station can attempt to deliver content tothe systems of a set (e.g., tens, hundreds, thousands, etc.) ofvehicles. In some implementations, the content can be sent via amulticast transmission (e.g., an LTE multicast transmission) from anEvolved Multimedia Broadcast Multicast Services (eMBMS) core via thebase station to the systems of a set of vehicles. In someimplementations, the content can include information concerning statusdata of nearby infrastructure, traffic data, data related to safetyhazards, and/or the like. In some implementations, the set of vehiclescan include a first vehicle (e.g., vehicle 1), such that the firstvehicle is within the service area of the base station and the system ofthe first vehicle subscribes to the cellular connection serviceassociated with the base station. The system of the first vehicletherefore can communicate with the base station via the cellularconnection. In some implementations, the set of vehicles can include asecond vehicle (e.g., vehicle 2), such that the second vehicle isoutside of the service area of the base station, but within the relayarea of the first vehicle. In some implementations, the set of vehiclescan include multiple (e.g., tens, hundreds, thousands, etc.) secondvehicles, where each of the second vehicles is outside of the servicearea of the base station, but within the relay area of the firstvehicle. For clarity, this description provides examples of someimplementations that include the system of a single second vehicle, butthe description is applicable to implementations that include thesystems of multiple second vehicles. In some implementations, the set ofvehicles can include a third vehicle (e.g., vehicle 3), such that thethird vehicle is outside the service area of the base station andoutside the relay area of the first vehicle, but within the relay areaof the second vehicle. In some implementations, the set of vehicles caninclude multiple (e.g., tens, hundreds, thousands, etc.) third vehicles,where each of the third vehicles is outside of the service area of thebase station and outside the relay area of the first vehicle, but withinthe relay area of the second vehicle. For clarity, this descriptionprovides examples of some implementations that include the system of asingle third vehicle, but the description is applicable toimplementations including the systems of multiple third vehicles.

In some implementations, the system of each vehicle (e.g., the firstvehicle, the second vehicle, the third vehicle, and/or the like) caninclude a control unit and/or a telemetry device. In someimplementations, the control unit can include one or more electroniccontrol units, sensors, embedded devices, and/or the like. In someimplementations, the telemetry device can receive, via a vehiclecommunication network (VCN), telemetry information associated with thecontrol unit. For example, the control unit can provide the telemetryinformation to the telemetry device during operation of the vehicle. Insome implementations, the telemetry device can receive telemetryinformation from hundreds of control units of the vehicle. In someimplementations, the telemetry device can receive content transmittedfrom the base station via the cellular connection. In someimplementations, the telemetry device can send the content to thecontrol unit via the VCN, and the control unit can process the contentto affect the driving behavior of the vehicle. In some implementations,the control unit and/or the telemetry device can generate and sendmessages to and receive messages from a control unit and/or a telemetrydevice of another vehicle via a direct communications interface. Forexample, the control unit can generate an LTE PC5 message and send themessage to the control unit of another vehicle via the LTE PC5communications interface. In some implementations, the control unit caninclude a message manager that can generate and send messages to andreceive messages from a control unit of another vehicle via the directcommunications interface.

As shown by reference number 102, a base station can transmit content tothe system of a first vehicle (e.g., vehicle 1). In someimplementations, the base station can transmit the content to the systemof the first vehicle using a unicast, broadcast, and/or multicastcellular connection. For example, the base station can transmit thecontent, which indicates a traffic jam on the road ahead, to the systemof vehicle 1 using an LTE multicast connection. In some implementations,the system of the first vehicle can receive the content at the telemetrydevice associated with the first vehicle. As shown by reference number104, the first vehicle can store the content at the system of the firstvehicle. For example, the first vehicle can store the content at thetelemetry device associated with the first vehicle, which can include amulticast client component for receiving the content from the basestation and a telemetry repository component for storing the content.

In some implementations, the telemetry device of the first vehicle cansend a message (e.g., a first message) to the control unit of the firstvehicle to indicate that the base station transmitted the content to thetelemetry device at the first vehicle. For example, the telemetry deviceof the first vehicle can use a VCN interface to send the message to thecontrol unit of the first vehicle via the VCN of the first vehicle. Insome implementations, the control unit of the first vehicle can check tosee whether the base station transmitted content to the system of thefirst vehicle (by, e.g., sending a query to the telemetry device of thefirst vehicle on a schedule (e.g., every second, every 10 seconds, every100 seconds, and/or the like) regarding whether new content has beenreceived by the telemetry device of the first vehicle via the VCN of thefirst vehicle).

As shown by reference number 106, the control unit of the first vehiclecan receive the message that indicates that the base station transmittedcontent to the telemetry device of the first vehicle. In someimplementations, the control unit of the first vehicle can generate amessage that includes a query (e.g., a second message). For example, themessage can include a query to identify which vehicles are neighborvehicles of the first vehicle. In some implementations, a vehicle can bea neighbor vehicle of the first vehicle if the vehicle is located withinthe relay area (e.g., relay area 1) of the first vehicle. In someimplementations, a vehicle can be a neighbor vehicle of the firstvehicle if the vehicle is located within the relay area of the firstvehicle and/or if the vehicle is located within the relay area (e.g.,relay area 2) of a vehicle that is within the relay area of the firstvehicle. In some implementations, a vehicle can be a neighbor vehicle ofthe first vehicle if the vehicle is located within the relay area of thefirst vehicle and/or if the vehicle is located within the relay area ofanother neighbor vehicle.

As shown by reference number 108, the system of the first vehicle cansend the message that includes the query to the system of the secondvehicle. For example, the first vehicle can use the control unit of thefirst vehicle to send the message that includes the query to the controlunit of the second vehicle via a direct communications interface (e.g.,an LTE PC5 interface). The message that includes the query can bereceived by the system of the second vehicle (e.g., the telemetrydevice(s) and/or control unit(s) of the second vehicle). In someimplementations, the direct communications interface can be an LTE PC5interface, an IEEE 802.11p interface, and/or the like. As shown byreference number 110, the system of the second vehicle can send themessage that includes the query to the system of the third vehicle in asimilar manner to that described herein in relation to reference number108.

As shown in FIG. 1D, the neighbor vehicles of the first vehicle sendidentification information to the first vehicle. As shown by referencenumber 112, the system of the third vehicle can process the message thatincludes the query and, in response, create a message that includesidentification information that identifies the third vehicle. In someimplementations, the identification information that identifies thethird vehicle can include a make, a model, a model year, and/or the likeof the third vehicle. In some implementations, the identificationinformation that identifies the third vehicle can include a device class(e.g., whether the third vehicle is a consumer vehicle, a commercialvehicle, a vehicle for smart infrastructure, and/or the like) of thethird vehicle, a provider of the third vehicle (e.g., the fleet owner ofthe third vehicle), and/or the like. For example, the control unit ofthe third vehicle can create a message that includes identificationinformation that includes a make, a model, and a model year of the thirdvehicle. In some implementations, the system of the third vehicle cansend the message that includes the identification information thatidentifies the third vehicle to the system of the second vehicle via thedirect communications interface. For example, the control unit of thethird vehicle can send the message that includes identificationinformation that includes the make, model, and model year of the thirdvehicle to the control unit of the second vehicle via the LTE PC5interface.

In some implementations, the system of the second vehicle can receive,from the system of the third vehicle via the direct communicationsinterface, the message (e.g., a third message) that includes theidentification information that identifies the third vehicle. As shownby reference number 114, the system of the second vehicle can processthe message that includes the identification information that identifiesthe third vehicle and modify the message to also include identificationinformation that identifies the second vehicle. In some implementations,the system of the second vehicle can create a new message that includesthe identification information that identifies the second vehicle andidentification information that identifies the third vehicle. In someimplementations, the identification information that identifies thesecond vehicle can include a make, a model, a model year, a deviceclass, a provider, and/or the like of the second vehicle. For example,the message that includes the identification information that identifiesthe second vehicle and the identification information that identifiesthe third vehicle can include information that identifies the deviceclass (e.g., the second vehicle is a commercial vehicle) of the secondvehicle and the make and model of the third vehicle. In someimplementations, the system of the second vehicle can send the messagethat includes the identification information that identifies the secondvehicle and identification information that identifies the third vehicleto the system of the first vehicle via the direct communicationsinterface.

In some implementations, the system of the first vehicle can receive themessage (e.g., the third message) that includes the identificationinformation that identifies the second vehicle (e.g., first information)and identification information that identifies the third vehicle (e.g.,second information) from the system of the second vehicle via the directcommunications interface. As shown by reference number 116, the systemof the first vehicle can process the message (e.g., the third message)that includes the identification information that identifies the thirdvehicle and the identification information that identifies the secondvehicle to create a list of neighbor vehicles of the first vehicle andidentification information that identifies each neighbor vehicle. Forexample, the system of the first vehicle can receive the message thatincludes identification information that identifies the second vehicleand the third vehicle and create a list that indicates that the secondvehicle and the third vehicle are neighbor vehicles of vehicle 1. Insome implementations, the system of the first vehicle can send the listof neighbor vehicles to the base station via the cellular connection. Insome implementations, the system of the first vehicle can send the listof neighbor vehicles to the eMBMS core via the base station.

As shown in FIG. 1E, the base station can send a file to the firstvehicle to facilitate delivery of the content to the neighbor vehiclesof the first vehicle. As shown by reference number 118, the base stationcan send the file to the system of the first vehicle via the cellularconnection. In some implementations, the eMBMS core can send the filevia the base station to the system of the first vehicle via a multicasttransmission (e.g., an LTE multicast transmission). For example, theeMBMS core, via the base station, can send a multicast serviceannouncement file to the system of the first vehicle via an LTEmulticast connection. In some implementations, the file can include alink to the content. For example, the file can include a uniformresource locator (URL) link to the content.

As shown by reference number 120, the system of the first vehicle canparse the file to determine the link to the content. For example, thesystem of the first vehicle can parse the multicast service announcementfile to determine the link to the content. In some implementations, thesystem of the first vehicle can generate a message that includes thelink to the content. For example, the control unit of the first vehiclecan create a message that includes the URL link to the content. In someimplementations, the message that includes the link can includeinformation that identifies the first vehicle. In some implementations,the message that includes the link can include a device classidentifier, such that the message that includes the link can be readonly by the system of a vehicle of a device class indicated by thedevice class identifier.

As shown by reference number 122, the system of the first vehicle cansend the message that includes the link (e.g., a fourth message) to thesystem of the second vehicle via the direct communications interface.For example, the control unit of the first vehicle can send the messagethat includes the URL link to the content to the control unit of thesecond vehicle via an LTE PC5 interface. In some implementations,sending the message that includes the link to the content causes thesystem of the second vehicle to download the content via the link (e.g.,by communicating with another base station via a cellular connection)and send the message that includes the link to the content to the systemof the third vehicle, which causes the system of the third vehicle todownload the content via the link in a similar manner as the system ofthe second vehicle.

As shown by reference number 124, the system of the second vehicle canreceive the message that includes the link to the content from thesystem of the first vehicle via the direct communications interface. Insome implementations, the system of the second vehicle can parse themessage that includes the link, determine the link to the content, anddownload the content via the link. For example, the control unit of thesecond vehicle can parse the message that includes the URL link to thecontent, determine the URL link to the content, and download the contentvia the URL link over a cellular connection (e.g., a unicast connectionand/or the like) with another base station. In some implementations,where the message that includes the link also includes the device classidentifier, the system of the second vehicle can download the contentvia the link only if the device class of the second vehicle matches thedevice class identifier.

As shown by reference number 126, the system of the second vehicle cansend the message that includes the link to the system of the thirdvehicle via the direct communications interface. In someimplementations, the system of the second vehicle can add informationthat identifies the second vehicle to the message that includes the linkbefore sending the message that includes the link to the system of thethird vehicle via the direct communications interface.

As shown by reference number 128, the system of the third vehicle canreceive the message that includes the link to the content from thesystem of the second vehicle via the direct communications interface. Insome implementations, the system of the third vehicle can parse themessage that includes the link, determine the link to the content, anddownload the content via the link over a cellular connection withanother base station. In some implementations, where the message thatincludes the link also includes the device class identifier, the systemof the third vehicle can download the content via the link only if thedevice class of the third vehicle matches the device class identifier.

As shown in FIG. 1F, the system of the first vehicle determines whetherthe content was delivered to the neighbor vehicles of the first vehicleand sends a report to the base station. As shown by reference number130, the system of the third vehicle can create a status message thatincludes information that indicates whether the system of the thirdvehicle was able to download the content via the link. In someimplementations, the system of the third vehicle can send the statusmessage to the system of the second vehicle via the directcommunications interface. In some implementations, the system of thesecond vehicle can receive the status message via the directcommunications interface. As shown by reference number 132, the systemof the second vehicle can update the status message to includeinformation that indicates whether the system of the second vehicle wasable to download the content via the link. In some implementations, thesystem of the second vehicle can send the status message to the firstvehicle via the direct communications interface.

In some implementations, the system of the first vehicle can receive thestatus message (e.g., a fifth message) from the second vehicle via thedirect communications interface. In some implementations, the statusmessage includes information that indicates whether the systems of thesecond vehicle and the third vehicle, respectively, were able todownload the content via the link (e.g., third information). As shown byreference number 134, the system of the first vehicle can generate areport that includes the identification information that identifies thesecond vehicle (e.g., the first information), the identificationinformation that identifies the third vehicle (e.g., the secondinformation), and/or the information that indicates whether the systemsof the second vehicle and the third vehicle, respectively, were able todownload the content via the link (e.g., the third information). Forexample, the system of the first vehicle can create a report thatincludes identification information that identifies the second vehicleand the third vehicle and whether the system of the second vehicle andthe system of the third vehicle were able to download the content viathe link. As shown by reference number 136, the system of the firstvehicle can send the report (e.g., a sixth message) to the base stationvia the cellular connection. In some implementations, the system of thefirst vehicle can send the report to the eMBMS core via the basestation.

In this way, some implementations described herein permit delivery ofcontent to a system of a first vehicle, a system of a second vehiclethat is a neighbor vehicle of the first vehicle, and a system of a thirdvehicle that is a neighbor vehicle of the second vehicle. In this way,some implementations described herein allow the system of the firstvehicle to facilitate delivery of the content, which the system of thefirst vehicle received from a base station via a cellular connection, tothe system of the second vehicle and the system of the third vehicleeven if the second vehicle and the third vehicle are outside a servicearea of the base station and/or the system of the second vehicle and thesystem of the third vehicle do not subscribe to a cellular connectionservice associated with the base station. In this way, someimplementations allow for efficient network usage and efficient use ofnetwork bandwidth by efficient distribution of the content to the systemof the first vehicle, the system of the second vehicle, and the systemof the third vehicle. In this way, some implementations require reducedcommunication and/or signaling relative to communications between thebase station and the system of the first vehicle, the system of thesecond vehicle, and the system of the third vehicle. In this way, someimplementations described herein conserve processor and/or memoryresources of the systems associated with the first vehicle, the secondvehicle, and the third vehicle and the base station and/or conservenetwork resources. In this way, some implementations increase the amountof information that is available to the first vehicle, the secondvehicle, and the third vehicle, which can improve effectiveness,efficiency, and safety of how the first vehicle, the second vehicle, andthe third vehicle operate.

As indicated above, FIGS. 1A-1F are provided merely as examples. Otherexamples are possible and can differ from what was described with regardto FIGS. 1A-1F.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.2, environment 200 can include a base station 205, a vehicle 210, whichincludes a telemetry device 210-1 and a control device 210-2, a vehicle215, which includes a telemetry device 215-1 and a control device 215-2,a vehicle 220, which includes a telemetry device 220-1 and a controldevice 220-2, a Multimedia Broadcast/Multicast Service Gateway (MBMS-GW)225, a Broadcast-Multicast Service Center device (BMSC) 230. Devices ofenvironment 200 can interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

Some implementations are described herein as being performed within along term evolution (LTE) network for explanatory purposes. Someimplementations can be performed within a network that is not an LTEnetwork, such as a fifth generation (5G) network or a third generation(3G) network.

Environment 200 includes an evolved packet system (EPS) that includes anLTE network, an evolved packet core (EPC), and/or an Evolved MultimediaBroadcast Multicast Services (eMBMS) core that operates based on a thirdgeneration partnership project (3GPP) wireless communication standard.

The LTE network includes a radio access network (RAN) that includes oneor more base stations 205 that take the form of evolved Node Bs (eNBs)via which vehicle 210 communicates with the EPC and/or the eMBMS.

The eMBMS core can include MBMS-GW 225 and/or BMSC 230 that enable theeMBMS core to communicate with vehicle 210 using MBMS in associationwith the LTE network.

In some implementations, the eMBMS core can permit multicast services,such as unidirectional downlink transmissions from a cell to a set ofvehicles 210 (e.g., associated with a service area). Each vehicle 210can receive the downlink data (e.g., content) using the same set ofair-interface resources. In some implementations, the eMBMS core canpermit multicast services, such as unidirectional downlink transmissionsfrom a cell to a set of vehicles 210 (e.g., associated with a servicearea). In some implementations, vehicle 210 might be required to performspecific procedures prior to receiving downlink data associated with amulticast service implemented by the eMBMS core. For example, vehicle210 can perform subscription and/or joining procedures prior toreceiving downlink data associated with a multicast service. In thisway, the eMBMS core can provide a dedicated and secure network path formulticast transmissions to a particular service area. As used herein, aservice area can refer to an area in which downlink data belonging to aspecific eMBMS is transmitted.

In some implementations, eMBMS core can provide MBMS over a singlefrequency network (MBSFN), which corresponds to the simulcasttransmission of MBMS data. For example, an MBSFN can provide identicaldata streams from multiple time synchronized base stations 205 using thesame RF carrier. In this way, the eMBMS core provides a network path forthe downlink multicast delivery of downlink data within a service area,and provides dedicated and secure transmission of the downlink data to aservice area and/or a set of service areas.

Base station 205 includes one or more devices capable of transferringtraffic destined for and/or received from vehicle 210. In someimplementations, base station 205 can include an eNB associated with theLTE network that receives traffic from and/or sends traffic on the LTEnetwork. Additionally, or alternatively, one or more base stations 205can be associated with a RAN that is not associated with the LTEnetwork. Base station 205 can send traffic to and/or receive trafficfrom vehicle 210 via an air interface. In some implementations, basestation 205 can include a small cell base station, such as a basestation of a microcell, a picocell, and/or a femtocell.

Vehicle 210 includes one or more devices (e.g., telemetry device 210-1,control device 210-2, and/or the like) capable of communicating withbase station 205 and/or a network (e.g., the LTE network). For example,telemetry device 210-1 can include a wireless communication device, atelematics device, a radiotelephone, a personal communications system(PCS) terminal (e.g., that can combine a cellular radiotelephone withdata processing and data communications capabilities), a smart phone, alaptop computer, a tablet computer, and/or a similar device. In someimplementations, telemetry device 210-1 includes one or moremachine-to-machine (M2M) devices and/or one or more Internet of Things(IoT) devices (e.g., any “thing” in the IoT). Telemetry device 210-1 cansend traffic to and/or receive traffic from a network (e.g., the LTEnetwork via base station 205).

Vehicle 210 includes one or more devices (e.g., telemetry device 210-1,control device 210-2, and/or the like) capable of communicating withanother vehicle (e.g., vehicle 215). For example, control device 210-2can use short-range ad hoc and/or direct communications (e.g., LTE PC5communications, IEEE 802.11p communications, and/or the like) to sendtraffic to and/or receive traffic from vehicle 215.

Vehicle 210 includes one or more devices capable of receiving,generating, processing, storing, and/or providing telemetry informationand/or service area information (e.g., control device 210-2). Forexample, control device 210-2 can include an electronics control unit(ECU) (e.g., an engine control module (ECM), a powertrain control module(PCM), a transmission control module (TCM), a brake control module(BCM), a speed control unit (SCU), a telematics control unit (TCU), atransmission control unit (TCU), a battery management system, anelectronic power steering control unit (PSCU), or another controlmodule), a sensor (e.g., a fuel pressure sensor, an engine temperaturesensor, a tire pressure sensor, or another sensor), or the like.

In some implementations, control device 210-2 can include an embeddeddevice associated with controlling one or more systems or sub-systems ofa vehicle, such as an engine electronics system (e.g., a fuel injectionrate control system, an emission control system, a turbocharger controlsystem, a throttle control system, and/or the like), a transmissionelectronics systems (e.g., a gear shift system, a clutch system, and/orthe like), a chassis electronics system (e.g., an anti-lock brakingsystem (ABS), a traction control system (TCS), an electronic brakedistribution (EBD) system, an electronic stability program (ESP) system,and/or the like), a safety system (e.g., an airbag system, a hilldescent control system, an emergency brake assist system, and/or thelike), a driver assistance system (e.g., an advanced driver-assistancesystem (ADAS), a lane assist system, a speed assist system, a blind spotdetection system, a park assist system, an adaptive cruise controlsystem, a pre-collision assist system, and/or the like), an infotainmentsystem (e.g., a navigation system, a multimedia system, an informationaccess system, a heads up display system, and/or the like), anautonomous driving system (e.g., a radar system, a Lidar system, a GPSsystem, a computer vision system, a vehicle communication system, and/orthe like), and/or the like. In some implementations, control device210-2 can include a message manager for generating, sending, andreceiving messages according to a direct communications protocol.

Vehicle 215 includes similar devices to those of vehicle 210. Vehicle215 includes one or more devices (e.g., telemetry device 215-1, controldevice 215-2, and/or the like) capable of communicating with a basestation (e.g., a base station associated with a different carrier thanthe carrier associated with base station 205) and/or a network (e.g., a3G network). For example, telemetry device 215-1 can include a wirelesscommunication device, a telematics device, a radiotelephone, a personalcommunications system (PCS) terminal (e.g., that can combine a cellularradiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer,and/or a similar device. In some implementations, telemetry device 215-1includes one or more M2M devices and/or one or more IoT devices (e.g.,any “thing” in the IoT). Telemetry device 215-1 can send traffic toand/or receive traffic from a network (e.g., the 3G network via the basestation associated with a different carrier than the carrier associatedwith base station 205).

Vehicle 215 includes one or more devices (e.g., telemetry device 210-1,control device 210-2, and/or the like) capable of communicating withanother vehicle (e.g., vehicle 220). For example, control device 215-2can use short-range ad hoc and/or direct communications (e.g., LTE PC5communications, IEEE 802.11p communications, and/or the like) to sendtraffic to and/or receive traffic from vehicle 210 and/or vehicle 220.

Vehicle 215 includes one or more devices capable of receiving,generating, processing, storing, and/or providing telemetry informationand/or service area information (e.g., control device 215-2). Forexample, control device 215-2 can include an electronics control unit(ECU) (e.g., an engine control module (ECM), a powertrain control module(PCM), a transmission control module (TCM), a brake control module(BCM), a speed control unit (SCU), a telematics control unit (TCU), atransmission control unit (TCU), a battery management system, anelectronic power steering control unit (PSCU), or another controlmodule), a sensor (e.g., a fuel pressure sensor, an engine temperaturesensor, a tire pressure sensor, or another sensor), or the like.

In some implementations, control device 215-2 can include an embeddeddevice associated with controlling one or more systems or sub-systems ofa vehicle, such as an engine electronics system (e.g., a fuel injectionrate control system, an emission control system, a turbocharger controlsystem, a throttle control system, and/or the like), a transmissionelectronics systems (e.g., a gear shift system, a clutch system, and/orthe like), a chassis electronics system (e.g., an anti-lock brakingsystem (ABS), a traction control system (TCS), an electronic brakedistribution (EBD) system, an electronic stability program (ESP) system,and/or the like), a safety system (e.g., an airbag system, a hilldescent control system, an emergency brake assist system, and/or thelike), a driver assistance system (e.g., an advanced driver-assistancesystem (ADAS), a lane assist system, a speed assist system, a blind spotdetection system, a park assist system, an adaptive cruise controlsystem, a pre-collision assist system, and/or the like), an infotainmentsystem (e.g., a navigation system, a multimedia system, an informationaccess system, a heads up display system, and/or the like), anautonomous driving system (e.g., a radar system, a Lidar system, a GPSsystem, a computer vision system, a vehicle communication system, and/orthe like), and/or the like. In some implementations, control device215-2 can include a message manager for generating, sending, andreceiving messages according to a direct communications protocol.

Vehicle 220 includes similar devices to those of vehicle 210. Vehicle220 includes one or more devices (e.g., telemetry device 220-1, controldevice 220-2, and/or the like) capable of communicating with a basestation (e.g., a base station associated with a different carrier thanthe carrier associated with base station 205) and/or a network (e.g., a5G network). For example, telemetry device 220-1 can include a wirelesscommunication device, a telematics device, a radiotelephone, a personalcommunications system (PCS) terminal (e.g., that can combine a cellularradiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer,and/or a similar device. In some implementations, telemetry device 220-1includes one or more M2M devices and/or one or more IoT devices (e.g.,any “thing” in the IoT). Telemetry device 220-1 can send traffic toand/or receive traffic from a network (e.g., the 3G network via the basestation associated with a different carrier than the carrier associatedwith base station 205).

Vehicle 220 includes one or more devices (e.g., telemetry device 210-1,control device 210-2, and/or the like) capable of communicating withanother vehicle (e.g., vehicle 215). For example, control device 220-2can use short-range ad hoc and/or direct communications (e.g., LTE PC5communications, IEEE 802.11p communications, and/or the like) to sendtraffic to and/or receive traffic from vehicle 215.

Vehicle 220 includes one or more devices capable of receiving,generating, processing, storing, and/or providing telemetry informationand/or service area information (e.g., control device 220-2). Forexample, control device 220-2 can include an electronics control unit(ECU) (e.g., an engine control module (ECM), a powertrain control module(PCM), a transmission control module (TCM), a brake control module(BCM), a speed control unit (SCU), a telematics control unit (TCU), atransmission control unit (TCU), a battery management system, anelectronic power steering control unit (PSCU), or another controlmodule), a sensor (e.g., a fuel pressure sensor, an engine temperaturesensor, a tire pressure sensor, or another sensor), and/or the like.

In some implementations, control device 220-2 can include an embeddeddevice associated with controlling one or more systems or sub-systems ofa vehicle, such as an engine electronics system (e.g., a fuel injectionrate control system, an emission control system, a turbocharger controlsystem, a throttle control system, and/or the like), a transmissionelectronics systems (e.g., a gear shift system, a clutch system, and/orthe like), a chassis electronics system (e.g., an anti-lock brakingsystem (ABS), a traction control system (TCS), an electronic brakedistribution (EBD) system, an electronic stability program (ESP) system,and/or the like), a safety system (e.g., an airbag system, a hilldescent control system, an emergency brake assist system, and/or thelike), a driver assistance system (e.g., an advanced driver-assistancesystem (ADAS), a lane assist system, a speed assist system, a blind spotdetection system, a park assist system, an adaptive cruise controlsystem, a pre-collision assist system, and/or the like), an infotainmentsystem (e.g., a navigation system, a multimedia system, an informationaccess system, a heads up display system, and/or the like), anautonomous driving system (e.g., a radar system, a Lidar system, a GPSsystem, a computer vision system, a vehicle communication system, and/orthe like), and/or the like. In some implementations, control device220-2 can include a message manager for generating, sending, andreceiving messages according to a direct communications protocol.

MBMS-GW 225 includes one or more devices capable of routing packetsrelated to eMBMS. For example, MBMS-GW 225 can include a traffictransfer device, such as a gateway, a router, a modem, a switch, afirewall, a NIC, a hub, a bridge, a server device, an OADM, or any othertype of device that processes and/or transfers traffic. MBMS-GW 225 canreceive traffic from a network and/or other network devices, and cansend the received traffic to vehicle 210 via base station 205.

BMSC 230 includes one or more devices capable of receiving, generating,storing, processing, and/or providing information associated withproviding a service. For example, BMSC 230 can include a server device,a traffic transfer device (e.g., a router, a switch, a hub, etc.), or asimilar device. In some implementations, BMSC 230 can allocate bandwidthfor providing a multicast service, and/or can instruct other devicesassociated with providing the multicast service.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 can beimplemented within a single device, or a single device shown in FIG. 2can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 can perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300can correspond to base station 205, vehicle 210, telemetry device 210-1,control device 210-2, vehicle 215, telemetry device 215-1, controldevice 215-2, vehicle 220, telemetry device 220-1, and/or control device220-2. In some implementations, base station 205, vehicle 210, telemetrydevice 210-1, control device 210-2, vehicle 215, telemetry device 215-1,control device 215-2, vehicle 220, telemetry device 220-1, controldevice 220-2, MBMS-GW 225, BMSC 230, and/or the like can include one ormore devices 300 and/or one or more components of device 300. As shownin FIG. 3, device 300 can include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 can permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area network interface, a cellularnetwork interface, or the like.

Device 300 can perform one or more processes described herein. Device300 can perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 can causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 canperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a diagram of example components of a device 400. Device 400can correspond to telemetry device 210-1. In some implementations,vehicle 210 can include one or more devices 400 and/or one or morecomponents of device 400. As shown in FIG. 4, device 400 can include amulticast client component 410, a telemetry agent component 420, atelemetry repository component 430, a VCN interface component 440, avehicle communication network (VCN) 450, and/or control device 210-2.

Multicast client component 410 includes a component capable ofreceiving, generating, processing, storing, and/or providing telemetryinformation and/or information associated with external data sources(e.g., content). For example, multicast client component 410 can receivecontent from base station 205 and can store the content.

Telemetry agent component 420 includes a component capable of receiving,generating, processing, storing, and/or providing telemetry informationand/or content. For example, telemetry agent component 420 can receivetelemetry information from control device 210-2 and provide thetelemetry information to base station 205. Additionally, oralternatively, telemetry agent component 420 can receive content frommulticast client component 410 and provide the content to control device210-2.

Telemetry repository component 430 includes a component capable ofreceiving, generating, processing, storing, and/or providing telemetryinformation and/or content. For example, telemetry repository component430 can receive, from multicast client component 410, telemetryinformation and/or content and store the telemetry information and/orcontent for use by control device 210-2.

VCN interface component 440 includes a transceiver-like component, suchas a transceiver and/or a separate receiver and transmitter, thatpermits multicast client component 410, telemetry agent component 420,and/or telemetry repository component 430 to communicate with controldevice 210-2 via VCN(s) 450. In some implementations, multicast clientcomponent 410, telemetry agent component 420, and/or telemetryrepository component 430 can communicate with control device 210-2 viaVCN interface component 440 using a particular communication protocol.

VCN 450 includes one or more wired and/or wireless networks. Forexample, VCN 450 can include a network that allows telemetry device210-1 (e.g., multicast client component 410, telemetry agent component420, telemetry repository component 430, and/or VCN interface component440) to communicate with control device 210-2. In some implementations,VCN 450 can include a vehicle bus.

In some implementations, VCN 450 can operate using a message-basedprotocol network, such as a Society of Automotive Engineers (SAE) J1850pulse-width modulation (PWM) protocol network, an SAE J1850 variablepulse-width (VPW) protocol network, an International StandardsOrganization (ISO) 914102 protocol network, an ISO 14230 KeywordProtocol 2000 (KWP2000) network, an ISO 15765 Controller Area Network(CAN) protocol network (e.g., a CAN bus network), an SAE J2411Single-Wire CAN (SWC) protocol network, an SAE J19319 protocol network,an ISO 17458 protocol network (e.g., FlexRay), an Ethernet protocolnetwork, or the like. In some implementations, VCN 450 can facilitatethe transfer of telemetry information and/or content associated withcontrol device 210-2.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 canperform one or more functions described as being performed by anotherset of components of device 400.

FIGS. 5A-5B are diagrams of an example call flow 500 of exampleoperations capable of being performed by one or more devices of FIG. 2and/or one or more components of one or more devices of FIG. 2. Forexample, FIGS. 5A-5B are diagrams of an example call flow 500 for acarrier agnostic relay for delivering information to autonomousvehicles.

As shown in FIG. 5A, and by reference number 502, Evolved MultimediaBroadcast Multicast Services (eMBMS) core via base station 205 can sendcontent to telemetry device 210-1 of vehicle 210 in a similar manner tothat described herein in relation to FIG. 1C. As shown by referencenumber 504, telemetry device 210-1 of vehicle 210 can store the contentin a similar manner to that described herein in relation to FIG. 1C. Asshown by reference number 506, control device 210-2 of vehicle 210 cancheck to see if content has been received and stored at telemetry device210-1 of vehicle 210 in a similar manner to that described herein inrelation to FIG. 1C. As shown by reference number 508, control device210-2 of vehicle 210 can generate and send a message that includes aquery (e.g., a second message) to a system (e.g., telemetry device215-1, control device 215-2, and/or the like) of vehicle 215, which cansend the message to a system (e.g., telemetry device 220-1, controldevice 220-2, and/or the like) of vehicle 220, in a similar manner tothat described herein in relation to FIG. 1C. In addition, the system ofvehicle 220 can send an identification message (e.g., a third message)to the system of vehicle 215, which can send the identification messageto control device 210-2 of vehicle 210, in a similar manner to thatdescribed herein in relation to FIG. 1D. As shown by reference number510, control device 210-2 of vehicle 210 can receive the identificationmessage and generate a neighbor vehicle list in a similar manner to thatdescribed herein in relation to FIG. 1D. As shown by reference number512, the eMBMS core via base station 205 can send a file to telemetrydevice 210-1 of vehicle 210 in a similar manner to that described hereinin relation to FIG. 1E. As shown by reference number 514, control device210-2 of vehicle 210 can receive the file and parse the file todetermine a link to the content in a similar manner to that describedherein in relation to FIG. 1E. As shown by reference number 516, controldevice 210-2 of vehicle 210 can generate a message that includes thelink to the content (e.g., a fourth message) in a similar manner to thatdescribed herein in relation to FIG. 1E.

As shown in FIG. 5B, and by reference number 518, control device 210-2of vehicle 210 can send the message that includes the link to the systemof vehicle 215 in a similar manner to that described herein in relationto FIG. 1E. As shown by reference number 520, the system of vehicle 215can receive the message that includes the link and download the contentvia the link in a similar manner to that described herein in relation toFIG. 1E. As shown by reference number 522, the system of vehicle 215 cansend the message that includes the link to vehicle 220 in a similarmanner to that described herein in relation to FIG. 1E. As shown byreference number 524, the system of vehicle 220 can receive the messagethat includes the link and download the content via the link in asimilar manner to that described herein in relation to FIG. 1E. As shownby reference number 526, the system of vehicle 220 can send a downloadstatus message (e.g., a fifth message) to the system of vehicle 215,which can update and send the download status message to control device210-2 of vehicle 210 in a similar manner to that described herein inrelation to FIG. 1F. As shown by reference number 528, control device210-2 of vehicle 210 can receive the download status message and createa report (e.g., a sixth message) that includes information identifyingvehicle 215 and vehicle 220 and whether vehicle the systems of 215 andvehicle 220 were able to download the content via the link in a similarmanner to that described herein in relation to FIG. 1F. As shown byreference number 530, control device 210-2 of vehicle 210 can send thereport to the eMBMS core via base station 205 in a similar manner tothat described herein in relation to FIG. 1F.

As indicated above, FIGS. 5A-5B are provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIGS. 5A-5B.

FIG. 6 is a flow chart of an example process 600 for a carrier agnosticrelay for delivering information to autonomous vehicles. In someimplementations, one or more process blocks of FIG. 6 can be performedby a control device (e.g., control device 210-2). In someimplementations, one or more process blocks of FIG. 6 can be performedby another device or a group of devices separate from or including thecontrol device, such as a base station (e.g., base station 205), avehicle (e.g., vehicle 210, vehicle 215, vehicle 220, etc.), a telemetrydevice (e.g., telemetry device 210-1), MBMS-GW 225, BMSC 230, and/or thelike.

As shown in FIG. 6, process 600 can include receiving, from a telemetrydevice, a first message that indicates that a base station transmittedcontent to the telemetry device (block 610). For example, the controldevice (e.g., using processor 320, memory 330, storage component 340,input component 350, communication interface 370, and/or the like) canreceive, from a telemetry device, a first message that indicates that abase station transmitted content to the telemetry device, as describedabove in connection with FIGS. 1A-1F.

As further shown in FIG. 6, process 600 can include generating a secondmessage, wherein the second message includes a query (block 620). Forexample, the control device (e.g., using processor 320, memory 330,storage component 340, and/or the like) can generate a second message,as described above in connection with FIGS. 1A-1F. In someimplementations, the second message can include a query.

As further shown in FIG. 6, process 600 can include sending the secondmessage to a remote device via a direct communications interface (block630). For example, the control device (e.g., using processor 320, memory330, storage component 340, output component 360, communicationinterface 370, and/or the like) can send the second message to a remotedevice via a direct communications interface, as described above inconnection with FIGS. 1A-1F.

As further shown in FIG. 6, process 600 can include receiving, based onsending the second message, a third message from the remote device viathe direct communications interface, wherein the third message includesfirst information that identifies the remote device and secondinformation that identifies a neighbor device of the remote device(block 640). For example, the control device (e.g., using processor 320,memory 330, storage component 340, input component 350, communicationinterface 370, and/or the like) can receive, based on sending the secondmessage, a third message from the remote device via the directcommunications interface, as described above in connection with FIGS.1A-1F. In some implementations, the third message can include firstinformation that identifies the remote device and second informationthat identifies a neighbor device of the remote device.

As further shown in FIG. 6, process 600 can include generating a fourthmessage, wherein the fourth message includes a link to the content(block 650). For example, the control device (e.g., using processor 320,memory 330, storage component 340, and/or the like) can generate afourth message, as described above in connection with FIGS. 1A-1F. Insome implementations, the fourth message can include a link to thecontent.

Alternatively, as further shown in FIG. 6, process 600 can includegenerating a fourth message, wherein the fourth message includes a linkto the content and a device class identifier (block 655). For example,the control device (e.g., using processor 320, memory 330, storagecomponent 340, and/or the like) can generate a fourth message, asdescribed above in connection with FIGS. 1A-1F. In some implementations,the fourth message can include a link to the content and a device classidentifier.

As further shown in FIG. 6, process 600 can include sending the fourthmessage to the remote device via the direct communications interface,wherein sending the fourth message to the remote device causes theremote device to download the content via the link and send the fourthmessage to the neighbor device, which causes the neighbor device todownload the content via the link (block 660). For example, the controldevice (e.g., using processor 320, memory 330, storage component 340,output component 360, communication interface 370, and/or the like) cansend the fourth message to the remote device via the directcommunications interface, as described above in connection with FIGS.1A-1F. In some implementations, sending the fourth message to the remotedevice can cause the remote device to download the content via the linkand send the fourth message to the neighbor device, which can cause theneighbor device to download the content via the link.

As further shown in FIG. 6, process 600 can include receiving, based onsending the fourth message, a fifth message from the remote device viathe direct communications interface, wherein the fifth message includesthird information that indicates whether the remote device and theneighbor device downloaded the content via the link (block 670). Forexample, the control device (e.g., using processor 320, memory 330,storage component 340, input component 350, communication interface 370,and/or the like) can receive, based on sending the fourth message, afifth message from the remote device via the direct communicationsinterface, as described above in connection with FIGS. 1A-1F. In someimplementations, the fifth message can include third information thatindicates whether the remote device and the neighbor device downloadedthe content via the link.

As further shown in FIG. 6, process 600 can include generating, based onreceiving the fifth message, a sixth message, wherein the sixth messageincludes the first information, the second information, and the thirdinformation (block 680). For example, the control device (e.g., usingprocessor 320, memory 330, storage component 340, and/or the like) cangenerate, based on receiving the fifth message, a sixth message, asdescribed above in connection with FIGS. 1A-1F. In some implementations,the sixth message can include the first information, the secondinformation, and the third information.

As further shown in FIG. 6, process 600 can include sending the sixthmessage to the base station (block 690). For example, the control device(e.g., using processor 320, memory 330, storage component 340, outputcomponent 360, communication interface 370, and/or the like) can sendthe sixth message to the base station, as described above in connectionwith FIGS. 1A-1F.

Process 600 can include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the remote device can be associated with afirst vehicle, and the neighbor device can be associated with a secondvehicle. In some implementations, the first information can include amake of the first vehicle, a model of the first vehicle, a model year ofthe first vehicle, a device class of the first vehicle, and/or aprovider of the first vehicle. In some implementations, the secondinformation can include a make of the second vehicle, a model of thesecond vehicle, a model year of the second vehicle, a device class ofthe second vehicle, and/or a provider of the second vehicle.

In some implementations, the base station can have transmitted thecontent to the telemetry device via a Long-Term Evolution (LTE)multicast transmission. In some implementations, when generating thefourth message, the control device can receive an LTE multicast serviceannouncement file, can parse the LTE multicast service announcement fileto determine the link to the content, and can create the fourth messageto include the link to the content. In some implementations, the link tothe content can be a uniform resource locator (URL). In someimplementations, the direct communications interface can be a Long-TermEvolution (LTE) PC5 interface

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 can be performed in parallel.

In this way, some implementations described herein permit delivery ofcontent to a system (e.g., telemetry device 210-1, control device 210-2,and/or the like) of vehicle 210, a system (e.g., telemetry device 215-1,control device 215-2, and/or the like) of vehicle 215, and a system(e.g., telemetry device 220-1, control device 220-2, and/or the like) ofvehicle 220. In this way, some implementations described herein allowthe system of vehicle 210 to facilitate delivery of the content, whichthe system of vehicle 210 received from a base station via a cellularconnection, to the system of vehicle 215 and the system of vehicle 220even if vehicle 215 and vehicle 220 are outside a service area of thebase station and/or the system of vehicle 215 and the system of vehicle220 do not subscribe to a cellular connection service associated withthe base station. In this way, some implementations allow for efficientnetwork usage and efficient use of network bandwidth by efficientdistribution of the content to the system of vehicle 210, the system ofvehicle 215, and the system of vehicle 220. In this way, someimplementations require reduced communication and/or signaling relativeto communications between the base station and the system of vehicle210, the system of vehicle 215, and the system of vehicle 220. In thisway, some implementations described herein conserve processor and/ormemory resources of the systems associated with vehicle 210, vehicle215, and vehicle 220 and the base station and/or conserve networkresources. In this way, some implementations increase the amount ofinformation that is available to vehicle 210, vehicle 215, and vehicle220, which can improve effectiveness, efficiency, and safety of howvehicle 210, vehicle 215, and vehicle 220 operate.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device andfrom a telemetry device associated with a first vehicle, a first messagethat indicates that a base station transmitted content relating tovehicle operation to the telemetry device; processing, by the device andbased on receiving the first message, the content to affect drivingbehavior of the first vehicle; generating, by the device, a secondmessage, wherein the second message includes a query; sending, by thedevice, the second message to a remote device associated with a secondvehicle via a direct communications interface; receiving, by the deviceand based on sending the second message, a third message from the remotedevice via the direct communications interface, wherein the thirdmessage includes first information that identifies the remote device andsecond information that identifies a neighbor device of the remotedevice, wherein the neighbor device is associated with a third vehicle;generating, by the device, a fourth message, wherein the fourth messageincludes a link to the content; sending, by the device, the fourthmessage to the remote device via the direct communications interface,wherein sending the fourth message to the remote device causes theremote device to download the content via the link and send the fourthmessage to the neighbor device, which causes the neighbor device todownload the content via the link, wherein, by downloading the content,the remote device and the neighbor device process the content to affectdriving behavior of the second vehicle and the third vehicle,respectively; receiving, by the device and based on sending the fourthmessage, a fifth message from the remote device via the directcommunications interface, wherein the fifth message includes thirdinformation that indicates whether the remote device and the neighbordevice downloaded the content via the link; generating, by the deviceand based on receiving the fifth message, a sixth message, wherein thesixth message includes the first information, the second information,and the third information; and sending, by the device, the sixth messageto the base station.
 2. The method of claim 1, wherein sending thefourth message to the remote device comprises: sending the fourthmessage to the remote device when the second vehicle is outside aservice area of the base station and within a first relay area of thefirst vehicle.
 3. The method of claim 1, wherein the first informationincludes at least one of: a make of the second vehicle, a model of thesecond vehicle, a model year of the second vehicle, a device class ofthe second vehicle, or a provider of the second vehicle.
 4. The methodof claim 1, wherein the second information includes at least one of: amake of the third vehicle, a model of the third vehicle, a model year ofthe third vehicle, a device class of the third vehicle, or a provider ofthe third vehicle.
 5. The method of claim 1, wherein the base stationtransmitted the content to the telemetry device via a Long-TermEvolution (LTE) multicast transmission.
 6. The method of claim 5,wherein generating the fourth message comprises: receiving an LTEmulticast service announcement file; parsing the LTE multicast serviceannouncement file to determine the link to the content, wherein the linkto the content is a uniform resource locator (URL); and creating thefourth message to include the link to the content.
 7. The method ofclaim 1, wherein the direct communications interface is a Long-TermEvolution (LTE) PC5 interface.
 8. A device, comprising: one or morememory devices; and one or more processors, operatively coupled to theone or more memory devices, to: receive, from a telemetry deviceassociated with a first vehicle, a first message that indicates that abase station transmitted content relating to vehicle operation to thetelemetry device; process the content to affect driving behavior of thefirst vehicle; generate a second message, wherein the second messageincludes a query; send the second message to a remote device associatedwith a second vehicle via a direct communications interface; receive,based on sending the second message, a third message from the remotedevice via the direct communications interface, wherein the thirdmessage includes first information that identifies the remote device andsecond information that identifies a neighbor device of the remotedevice, wherein the neighbor device is associated with a third vehicle;generate a fourth message, wherein the fourth message includes a link tothe content; send the fourth message to the remote device via the directcommunications interface, wherein sending the fourth message to theremote device causes the remote device to download the content via thelink and send the fourth message to the neighbor device, which causesthe neighbor device to download the content via the link, wherein, bydownloading the content, the remote device and the neighbor deviceprocess the content to affect driving behavior of the second vehicle andthe third vehicle, respectively; receive, based on sending the fourthmessage, a fifth message from the remote device via the directcommunications interface, wherein the fifth message includes thirdinformation that indicates whether the remote device and the neighbordevice downloaded the content via the link; generate, based on receivingthe fifth message, a sixth message, wherein the sixth message includesthe first information, the second information, and the thirdinformation; and send the sixth message to the base station.
 9. Thedevice of claim 8, wherein, the one or more processors, when sending thefourth message to the remote device, are to: send the fourth message tothe remote device when the second vehicle is outside a service area ofthe base station and within a first relay area of the first vehicle. 10.The device of claim 8, wherein the first information includes at leastone of: a make of the second vehicle, a model of the second vehicle, amodel year of the second vehicle, a device class of the second vehicle,or a provider of the second vehicle.
 11. The device of claim 8, whereinthe second information includes at least one of: a make of the thirdvehicle, a model of the third vehicle, a model year of the thirdvehicle, a device class of the third vehicle, or a provider of the thirdvehicle.
 12. The device of claim 8, wherein the base station transmittedthe content to the telemetry device via a Long-Term Evolution (LTE)multicast transmission.
 13. The device of claim 12, wherein the one ormore processors, when generating the fourth message, are to: receive anLTE multicast service announcement file; parse the LTE multicast serviceannouncement file to determine the link to the content, wherein the linkto the content is a uniform resource locator (URL); and create thefourth message to include the link to the content.
 14. The device ofclaim 8, wherein the direct communications interface is a Long-TermEvolution (LTE) PC5 interface.
 15. A non-transitory computer-readablemedium storing instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors of a device,cause the one or more processors to: receive, from a telemetry deviceassociated with a first vehicle, a first message that indicates that abase station transmitted content relating to vehicle operation to thetelemetry device; process the content to affect driving behavior of thefirst vehicle; generate a second message, wherein the second messageincludes a query; send the second message to a remote device associatedwith a second vehicle via a direct communications interface; receive,based on sending the second message, a third message from the remotedevice via the direct communications interface, wherein the thirdmessage includes first information that identifies the remote device andsecond information that identifies a neighbor device of the remotedevice, wherein the neighbor device is associated with a third vehicle;generate a fourth message, wherein the fourth message includes a link tothe content; send the fourth message to the remote device via the directcommunications interface, wherein sending the fourth message to theremote device causes the remote device to download the content via thelink and send the fourth message to the neighbor device, wherein, bydownloading the content, the remote device processes the content toaffect driving behavior of the second vehicle; receive, based on sendingthe fourth message, a fifth message from the remote device via thedirect communications interface, wherein the fifth message includesthird information that indicates whether the remote device and theneighbor device downloaded the content via the link; generate, based onreceiving the fifth message, a sixth message, wherein the sixth messageincludes the first information, the second information, and the thirdinformation; and send the sixth message to the base station.
 16. Thenon-transitory computer-readable medium of claim 15, wherein, the one ormore instructions, that cause the one or more processors to send thefourth message to the remote device, cause the one or more processorsto: send the fourth message to the remote device when the second vehicleis outside a service area of the base station and within a first relayarea of the first vehicle.
 17. The non-transitory computer-readablemedium of claim 15, wherein the first information includes at least oneof: a make of the second vehicle, a model of the second vehicle, a modelyear of the second vehicle, a device class of the second vehicle, or aprovider of the second vehicle.
 18. The non-transitory computer-readablemedium of claim 15, wherein the base station transmitted the content tothe telemetry device via a Long-Term Evolution (LTE) multicasttransmission.
 19. The non-transitory computer-readable medium of claim18, wherein the one or more instructions, that cause the one or moreprocessors to generate the fourth message, cause the one or moreprocessors to: receive an LTE multicast service announcement file; parsethe LTE multicast service announcement file to determine the link to thecontent, wherein the link to the content is a uniform resource locator(URL); and create the fourth message to include the link to the content.20. The non-transitory computer-readable medium of claim 15, wherein thedirect communications interface is a Long-Term Evolution (LTE) PC5interface.